Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

when subscriber can not get argo pod logs, make pod log message intuitive #4926

Open
wants to merge 8 commits into
base: master
Choose a base branch
from

Conversation

kwx4957
Copy link
Contributor

@kwx4957 kwx4957 commented Oct 19, 2024

Proposed changes

Fix: #4532

When subscriber pods fail to get from workflow pod or CR pod, the imported logs always return the same value. This is not intuitive for users.

So, by getting the phase state from the chaos experiment run, make the log message different for each experiment phase.

But the problem remains. I'm not sure which is the best way to write the logs.

	switch phase {
	case "Completed":
		return "Experiment pod is deleted"
	case "Stopped":
		return "Stopped"
	case "Running":
		return "Workflow Pod is initializing"
	case "Queue":
		return "Queue"
	case "NA":
		return "NA"
	case "Terminated":
		return "Terminated"
	case "Completed_With_Error":
		return "Completed_With_Error"
	case "Timeout":
		return "Timeout"
	case "Error":
		return "it can't run experiment"
	default:
		return "Workflow Pod is initializing"
	}
  • completed
    image
  • stopped
    image
  • Running
when workflow pod isn't ready workflow pod is ready, log is changed
image image

@kwx4957 kwx4957 changed the title when experiment run can not get argo pod logs, make pod log message intuitive when subscriber can not get argo pod logs, make pod log message intuitive Oct 19, 2024
@namkyu1999
Copy link
Member

Can you show us result screenshots? @kwx4957

@kwx4957
Copy link
Contributor Author

kwx4957 commented Oct 19, 2024

yes i will add it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: In Review
Development

Successfully merging this pull request may close these issues.

"Failed to get argo pod logs" is not intuitive
2 participants